Systems and methods for providing transaction provenance of off-chain transactions using distributed ledger transactions with secured representations of distributed ledger addresses of transacting parties

ABSTRACT

Implementations of the disclosure are directed to proving and creating on a distributed ledger a verifiable transaction record of a transaction between a user associated with user device and an agent associated with agent system, where the identities of the user and agent are hidden.

DESCRIPTION OF THE RELATED ART

The digital world relies heavily on the use of identity fortransactions, access to records, and verification of claims. Besidespersonal names, identity is typically assigned, generated, granted,and/or controlled by a central authority.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure, in accordance with one or more variousembodiments, is described in detail with reference to the followingfigures. The drawings are provided for purposes of illustration only andmerely depict typical or example embodiments.

FIG. 1 is a diagram illustrating an example environment for proving andcreating on a blockchain a verifiable transaction record of atransaction between a user associated with user device and an agentassociated with the agent system, where the identities of the user andagent are hidden, in accordance with implementations of the disclosure.

FIG. 2 is a block diagram illustrating an example architecture ofcomponents of a location beacon, in accordance with implementations ofthe disclosure.

FIG. 3 is a block diagram illustrating an example architecture of a userdevice, in accordance with implementations of the disclosure.

FIG. 4 is a block diagram illustrating an example architecture of anagent system, in accordance with implementations of the disclosure.

FIG. 5 is a block diagram illustrating an example architecture of anoff-chain verifier server system, in accordance with implementations ofthe disclosure.

FIG. 6 is a block diagram illustrating an example architecture of asecured identity server system, in accordance with implementations ofthe disclosure.

FIG. 7 is a sequence diagram illustrating a particular example methodthat may be implemented in the environment of FIG. 1 to create averifiable blockchain transaction record of a transaction between a userassociated with user device and an agent associated with an agentsystem, where the identities of the user and agent are hidden, inaccordance with implementations of the disclosure.

FIG. 8 is an operational flow diagram illustrating an example methodthat may be implemented by a user of user device, in accordance withimplementations of the disclosure.

FIG. 9 is an operational flow diagram illustrating an example methodthat may be implemented by agent system, in accordance withimplementations of the disclosure.

FIG. 10 is an operational flow diagram illustrating an example methodthat may be implemented by an off-chain verifier, in accordance withimplementations of the disclosure.

FIG. 11 is an operational flow diagram illustrating an example methodthat may be implemented by secured identity verifier, in accordance withimplementations of the disclosure.

FIG. 12 illustrates one example sequence diagram illustrating aparticular example method that may be implemented in the environment ofFIG. 1 to mask the second secured representation of the user blockchainaddress and create a verifiable blockchain transaction record of atransaction between a user associated with a user device and an agentassociated with an agent system, where the identities of the user andagent are hidden, in accordance with implementations of the disclosure.

FIG. 13 is an operational flow diagram illustrating an example methodthat may be implemented by a user of a user device, in accordance withimplementations of the disclosure.

FIG. 14 is an operational flow diagram illustrating an example methodthat may be implemented by a server system, in accordance withimplementations of the disclosure.

FIG. 15 illustrates an example environment by which a distributedattestation may be presented as a verifiable claim by an attestationholder associated with attestation holder device to a third partyverifier associated with third party verifier system, in accordance withimplementations of the disclosure.

FIG. 16 illustrates an example architecture of components of anattestation holder device, in accordance with implementations of thedisclosure.

FIG. 17 illustrates an example architecture of components of a thirdparty verifier system, in accordance with implementations of thedisclosure.

FIG. 18 illustrates an example architecture of components of securedidentity verifier server system, in accordance with implementations ofthe disclosure.

FIG. 19 is an operational flow diagram illustrating an example methodthat may be implemented by an attestation holder device, in accordancewith implementations of the disclosure.

FIG. 20 is an operational flow diagram illustrating an example methodthat may be implemented by a third party verifier system (e.g., a serversystem), in accordance with implementations of the disclosure.

FIG. 21 is an operational flow diagram illustrating an example methodthat may be implemented by a secured identity verifier (e.g., a serversystem), in accordance with implementations of the disclosure.

FIG. 22 illustrates an example of distributed attestation that may bepresented by a user to a verifier during a verifiable claims process, inaccordance with implementations of the disclosure.

FIG. 23 illustrates an example of distributed attestation that may bepresented by a user to a verifier during a verifiable claims process, inaccordance with implementations of the disclosure.

FIG. 24 illustrates an example of distributed attestation that may bepresented by a user to a verifier during a verifiable claims process, inaccordance with implementations of the disclosure.

The figures are not intended to be exhaustive or to limit variousembodiments to the precise form disclosed.

DETAILED DESCRIPTION

As used herein, the term “distributed ledger” generally refers to ashared digital ledger that is decentralized and shared between nodesdistributed across a network. After a transaction that is approved to bewritten to the ledger is consented by at least the majority of thenodes, the contents of the ledger are synchronized across all the nodes.Different types of consensus mechanisms that bring in varying levels ofprocessing requirements to agree on a transaction amongst distributednodes may be utilized in a distributed ledger network. Examples ofcommon consensus mechanisms include proof of work, proof of stake, proofof elapsed time, Kafka, etc. Various platforms have adopted differentconsensus mechanisms.

Distributed ledger technology (DLT) describes the superset of thedifferent variations of this technology. One presently popular type ofDLT is blockchain technology. While in a distributed ledger atransaction is written to the ledger after consensus, the requirement ismore specific in a blockchain: transactions are aggregated in to a blockand the block is appended to the last block of an existing linear chainof blocks. As such, all blockchains are a form of a distributed ledger,but all distributed ledgers are not necessarily a blockchain. BITCOINand ETHEREUM are examples of blockchain-based platforms. Directedacyclic graphs (DAG) are another example of a common form of DLT. IOTAis an example of a DAG-based platform. HYPERLEDGER is an example of aDLT-based platform. Unless explicitly stated otherwise, implementationsof the disclosure may apply to any variant of DLT, includingblockchains, DAGs, etc.

Although embodiments of the disclosure will be primarily described inthe context of blockchains, it should be appreciated that allembodiments, unless expressly stated otherwise, may be applied to othervariants of distributed ledger technology. For example, to the extent anembodiment is described in the context of a blockchain network sharing ablockchain, it should be appreciated that the embodiment may moregenerally be applied in a distributed ledger network sharing adistributed ledger. Similarly, to the extent that an embodiment recitesa “blockchain address,” a “secured representation of a blockchainaddress,” “a blockchain application,” or “a blockchain transaction,” itshould be appreciated that the embodiment may more generally be appliedusing a “distributed ledger address,” “a secured representation of adistributed ledger address,” “a distributed ledger application,” and/or“a distributed ledger transaction.”

As used herein, the term “public blockchain” generally refers to ablockchain that is accessible to any entity and whereby any entity mayparticipate in the consensus process. A public blockchain may bereferred to as a “fully decentralized” blockchain.

As used herein, the term “private blockchain” generally refers to ablockchain where a limited set of trusted entities participate in ablockchain network. A permissioned set of trusted nodes may participatein the consensus process. For example, a consortium of multiplefinancial institutions may form a private blockchain network. The rightto read a private blockchain may be public or restricted to trustednodes. A private blockchain may be referred to as a permissionedblockchain. Although implementations of the disclosure will primarily bedescribed in the context of private blockchains that are implemented byconsortiums, it should be appreciated that the technology disclosedherein may be adapted for use in anything from public to privateblockchains.

As used herein, the term “blockchain address” refers to an identifierfor a receiver or a sender in a blockchain transaction. A uniqueblockchain address may be associated with a person, an animal, acorporation, a location, an asset, or some other thing.

As used herein, the terms “off-chain” and “off-chain transaction” referto transactions that do not occur within a blockchain.

As used herein, the term “smart contract” refers to self-executing coderesiding on a blockchain network, which automates execution of contractsbetween trusted parties based on events on a blockchain or distributedledger.

As used herein, the term “blockchain wallet” refers to a digital walletthat helps manage a user's blockchain account(s), including private andpublic keys associated with the identity owning the wallet. For example,in particular implementations, a blockchain wallet may be to managecryptocurrency accounts.

As used herein, the term “secured representation of a blockchainaddress” generally refers to a value (e.g., a number in decimal format,hexadecimal format, etc.) that is generated by applying a time-basedcryptographic hashing algorithm to a blockchain address.

As used herein, the terms “time-based one-time advertisement,” “RN,”“random number advertisement” and “TOTA” generally refer to a messageincluding a one-time value generated by applying a cryptographic hashfunction using a blockchain address and a current timestamp. Thegenerated one-time value may be referred to as an example of a “securedrepresentation of a blockchain address.” The TOTA may only be valid fora short period of time and only for one time usage. This short durationmay be configured by a network administrator based on businessrequirement(s). The reason for limited usage of the advertisement may beto ensure that repeated usage of the advertisement is not nefariouslydone by people who have moved away from the location but want to use thesame advertisement as their proof of being there.

As used herein, the term “fixed advertisement” generally refers to aprintout or other display of a secured representation of a blockchainaddress that does not change over time. For example, a fixedadvertisement may comprise a printed or electronic code such as a QR orpassive RFID code that embeds a secured representation of a blockchainaddress that does not change over time. As fixed advertisements do notchange over time, a fixed relationship between the securedrepresentations of the blockchain addresses of the fixed advertisementand their respective clear versions may be maintained in a databasetable or other suitable data structure. The data structure may bereferred to during verification to determine a clear version of ablockchain address corresponding to a fixed advertisement.

As used herein, the terms “interactive proving mechanism” and“interactive proving protocol” refer to a process whereby a verifier(e.g., a server system operating on a blockchain network) asks a prover(e.g., a client device) to answer one or more questions that require theprover to capture one or more secured representations of blockchainaddresses. For example, an interactive proving mechanism may beperformed to prove that an individual (e.g., an individual carrying aclient device) is at a particular location at a particular time. Asanother example, an interactive proving mechanism may be performed toprove that an individual (e.g., an individual carrying a client device)has custody of an asset at a particular location and time. Everyiteration of questioning after a first round of receiving data from theprover may prove the validity of a claim with higher confidence. In somecases, just the first round of questioning may be needed. The number ofiterations and types of questions that are asked may vary depending uponthe business application.

As used herein, the term “distributed attestation” generally refers to averifiable claim that is written to a blockchain. For example, adistributed attestation may be a verifiable claim that attests to thepresence of an entity at a particular location and time, a verifiableclaim that attests to the custody of an asset by a user at a particularlocation and time, or some other verifiable claim. A distributedattestation may be reusable to verify a claim to various entities. Adistributed attestation may include a secured representation of ablockchain address of an entity associated with a claim and/or a securedrepresentation of a blockchain address of a location associated with aclaim. A permissioned entity may be configured to verify the claim bydetermining clear versions of the secured representations of theblockchain addresses.

As used herein, the term “attestation holder” generally refers to aparty to whom an attestation has been issued after verification of apast transaction by a verifier. This attestation may be a distributedattestation which may be used as a verifiable claim. The attestation maybe issued to the attestation holder in a specific context which may alsobe captured in the attestation. The attestation holder may present adistributed attestation as a claim to another party to prove to thethird party just what needs to be proved without any additionalinformation, which may also include the identity of the attestationholder being secured by a secure representation which is verifiable by averifier. In some cases, the attestation holder may present adistributed attestation as a claim to a third party that was notinvolved in a transaction attested to in the distributed attestation.For example, an attestation holder may be a purchaser of a televisionset presenting a distributed attestation as a claim to a service centerthat repairs televisions. The service center may submit the attestationpresented by the claimed purchaser to a distributed verifier, who canconfirm to the service center that the claimant of the attestation isactually the original owner of the TV and the actual attestation ownerof the transaction by validating the secure identity embedded into theattestation presented.

As used herein, the term “centralized identity” generally refers to anidentity of an entity that is created off-chain and maintained by acentralized entity. For example, a centralized identity may refer to ausername maintained on an active directory service, an email addressassociated with a domain, etc.

To prevent transaction fraud and abuse of customer information by thirdparties, there is a need for a secure way of validating and recordingtransactions by all parties involved in the transaction. In particular,there is a need for a method that both: i) creates a record that provesthat a transaction happened at a particular place and time betweenparties; and ii) prevents customer information (e.g., bankcard data)from being misused by third parties that may reside anywhere in theworld, but claiming that they are customers by spoofing identity andconducting transactions with forged card data. First, some presentmethods for proving location of a transaction rely on global positioningsystem (GPS) and/or IP based location proofs that may be manipulated byspoofing the system into believing they are present at a specificphysical location when in fact they are not. Additionally, although manypresent systems rely on a customer's signature (e.g., on a display of apoint of sale (POS) terminal or printed receipt) to prove that atransaction occurred, signatures may be easily forged. Second, misuse ofcustomer information has been a problem in some systems in the bankingindustry, where bankcard data has been stolen by attackers who gainaccess to the cards and/or who attach their own counterfeit card readerto a legitimate card reader (such as at an ATM terminal) to skim thebankcard data from an unwitting customer when the customer uses the cardreader.

To this end, implementations of the disclosure are directed to systemsand methods for creating, on a distributed ledger, a verifiable recordof a transaction between two parties that includes securedrepresentations of distributed ledger addresses to hide the identitiesof the parties and/or transaction location involved of the transaction.By virtue of implementing the systems and methods described herein: i) averifiable record of a transaction may be created on a distributedledger; and ii) the identity of parties involved in the transaction maybe hidden such that only approved parties may validate and/or reviewrecorded transactions. This may mandate a party to be present in alocation and capture location specific and transaction specificadvertisements. This may allow, for example, a party (e.g., customer ormerchant) to realize the benefits of creating a transaction record on apublic distributed ledger that is difficult, if not almost impossible,to tamper with, while maintaining the party's privacy.

Method and System for Blockchain and Verifiable Claim Based TransactionProvenance

FIG. 1 is a diagram illustrating an example environment for proving andcreating on a blockchain 800 a verifiable transaction record of atransaction between a user associated with user device 200 and an agentassociated with agent system 300, where the identities of the user andagent are hidden, in accordance with implementations of the disclosure.FIG. 1 will be described in conjunction with FIGS. 2, 3, 4, 5, and 6which are block diagrams respectively illustrating an examplearchitecture of components of a location beacon 100, user device 200,agent system 300, off-chain verifier 400, and secure-identity verifier500, in accordance with implementations of the disclosure. By way ofexample, the environment of FIG. 1 may be to prove and create averifiable record of a purchase transaction between a customer and amerchant, where the customer exchanges funds from a bank account inexchange for a product. In such an example, user device 200 may comprisea mobile device (e.g., smartphone) of the customer, agent system 300 maycomprise a point of sale (POS) terminal of the merchant, off-chainverifier 400 may be a server system of an off-chain banking authority,and secured identity verifier 500 may be a server of a central bankingauthority.

In the example of FIG. 1, a verifiable record of the transaction iscreated on a blockchain 800, copies of which may be maintained by nodeson blockchain network 700. As further described below, to maintain theprivacy of the transacting user and agent, the record of the transactionon blockchain 800 may use secured representations of blockchain address(e.g., random numbers) to mask the identities of the transactingparties, the location of the transaction, and other transaction details.

Blockchain network 700 may be a public blockchain network or consortiumblockchain network. In particular implementations, blockchain network700 may be implemented as a consortium of banks, merchants, andcustomers that operate the blockchain for applications such as verifyingand proving transactions between customers (e.g. user of user device200) and merchants (e.g., merchant associated with agent system 300),and for creating distributed attestations of transactions. Blockchainnetwork 300 may include a plurality of nodes (e.g., user device 200,agent system 300, secured identity verifier 500, and other components asneeded depending on the type of blockchain implementation) that mayread, write and/or validate transactions. Some or all blockchain nodesmay store a respective copy of a blockchain 800 that contains a recordof transactions, including blockchain transactions that includereferences to off-chain transactions made between user devices 200 andagent systems 300. In some implementations, nodes on blockchain network700 (e.g. user device 200) may be able to read transactions, but notwrite and/or verify transactions. Although the example of FIG. 1illustrates a blockchain 800 implemented as a linked-list of linearblocks, it should be appreciated that the systems and methods describedherein may be implemented with any other distributed ledger.

Communications between client device 200, agent system 300, off-chainverifier 400, secured identity verifier 500, blockchain address mappingserver system 600, and/or blockchain network 700 may occur over anysuitable communication medium. Some non-limiting examples ofcommunication mediums over which communications may occur include, forexample: wired communications mediums, such as cable, fiber-optic, orDSL; wireless communications mediums, such as Wi-Fi®, cellularcommunications, or satellite communications; or some combinationthereof. One or more access points (APs) may enable communications. AnAP may refer to an access network node that can be used by an electronicdevice to gain access to a network. An AP may be part of a wirelessnetwork (e.g., a Wi-Fi® network). An AP may refer to a Wide AreaNetwork) WAN or Low Power Wide Area Network (LPWAN) base station ortransmission system base station, another low power long range accessnetwork (e.g., LORA and SIGFOX) node, or an access node of a cellularnetwork. An AP 276 may include a bridge, switch or router (or multipleswitches/routers) to allow for communication between different devices.

A location beacon device 100 is configured to transmit (e.g., broadcast)a beacon including a secured representation of a location's blockchainaddress (e.g., RN-L1). In particular, each location beacon device 100may be provisioned with a blockchain address 113 that is associated witha particular location in the real world from which the location beacondevice 100 transmits beacons. To this end, each location beacon device100 may remain fixed to the location corresponding to its provisionedblockchain address 113.

For example, a provisioned blockchain address 113 may be used toidentify a pair of longitudinal and latitudinal coordinates, a specificindoor location (e.g., a store or purchase terminal location), aspecific outdoor location, an object having a fixed and known location,etc. In some implementations, the location may comprise a geographicalarea or range from which signals may be received from the locationbeacon device 100 (e.g., before signal attenuation). A mapping betweeneach provisioned blockchain address 113 and its associated location maybe maintained by a central entity such as a node on blockchain network700 or a device that is off-chain. For example, a blockchain addressmapping server system 600 may maintain a mapping between a provisionedlocation blockchain address and an associated location in a locationblockchain address database 691. This mapping may be taken care ofduring the provisioning process. It should be noted that although asingle location beacon device 100 is illustrated in the example of FIG.1, in some implementations, the environment may have multiple locationbeacon devices 100.

By virtue of a location beacon 100 transmitting a secured representationof a location blockchain address, which is associated with a location,information broadcast by a location beacon 100 may be secured fromexposure and tampering from unauthorized entities. The beacons used mayprevent tampering, preventing external parties from making any maliciouschanges in content, location, or operation, or copying information fromthe beacon. For example, when interactions using a blockchain address asan identifier of location occur in the open, passive sniffers or otherattacking devices may be able to gather location information belongingto an organization, but the advertisements being one time advertisementsare of no use after a particular short time period.

Each location beacon device 100 may include a machine readable medium110, a processing device 120, and a transmitter 130. The transmitter 130of location beacon device 100, in some implementations, may utilize ashort-range transmission technology such as Bluetooth®, Bluetooth® LowEnergy (BLE), radio-frequency identification (RFID), Wi-Fi®, Near-FieldCommunication (NFC), Zigbee, and the like. In other implementations, thelocation device 100 may utilize other transmission technologies such ascellular transmission, satellite transmission, LORA, SIGFOX, etc.

The machine readable medium 110 may store the location beacon device'sblockchain address 113, and a public key 111 and private key 112corresponding to the location blockchain address 113. For example, aprivate key 112 may be generated while creating a blockchain account, apublic key 111 may be derived from the private key, and a blockchainaddress 113 may be derived from the public key 111 by applyingadditional cryptographic algorithm(s). In some implementations, publickey 111 and location blockchain address 113 are the same, in which casemachine readable medium 110 may store private key 112 and blockchainaddress 113. Location beacon device 100 may be provisioned with publickey 111 (if different from blockchain address 113) and private key 112during configuration of location beacon device 100. Some deployments maynot require the private key to be provisioned to the location beacondevice, and in such cases it may just have the public key, theblockchain address, and/or an ID as a reference to the blockchainaddress.

Each location beacon device 100 may include time-based hash generationinstructions 114 that, when executed by processing device 120, apply atime-based cryptographic hashing algorithm to location blockchainaddress 113 to generate a secured representation of the locationblockchain address. The secured representation of the locationblockchain address may be generated by applying a one-time cryptographichashing algorithm using a current timestamp and the location blockchainaddress. The current timestamp may be obtained from processing device120 (e.g., from a clock of the processing device). A suitabletime-based, hash-based message authentication code (HMAC) algorithm maybe utilized to generate the secured representation of the blockchainaddress. As illustrated in the example of FIG. 1, application ofone-time cryptographic hashing algorithm generates a beacon including atime-based one time random number (RN-L1) including the securedrepresentation of the location blockchain address provisioned in beacondevice.

In some implementations, a location beacon device 100 may be implementedas a one-way communication device that broadcasts TOTAs. For example, alocation beacon device 100 may be implemented as a one-way Bluetooth®beacon transmitter.

Although location beacon device 100 is illustrated in FIG. 1 astransmitting beacons using radio frequency (RF) waves, it should beappreciated that, in some implementations, a location beacon device 100may transmit a beacon using some other communication method such as awired communication method (e.g., over coaxial and/or optical cables), afree space optical communication method (e.g., infrared, visible laser,etc.), or in a modulated soundwave (e.g., audible, subsonic, ultrasonic,etc.).

In an alternative implementation, a location beacon device 100 mayinstead be implemented as a device that displays data that is scanned toobtain a secured representation of its provisioned location blockchainaddress. For example, a location beacon device 100 may display a QR codeor other barcode including an embedded secured representation of thelocation blockchain address, and a user device 200, may scan the QR code(e.g., using a camera) to receive the secured representation of thelocation blockchain address. In such implementations, the securedrepresentation of the location blockchain address embedded in the QRcode may periodically change (e.g., depending on a configured time ofthe time-based hashing algorithm).

In another implementation, rather than having a location beacon device100 that broadcasts a secured representation of a blockchain address ordisplays a secured representation of a blockchain address, a fixedadvertisement having a secured representation of a location blockchainaddress may be scanned (e.g., by server provider system 300) to obtain asecured representation of a location blockchain addresses. As usedthroughout the disclosure, the term “scanning” may generally refer tousing any suitable scanning technique to read a value, including videoor image capture, infrared light capture, laser capture, manual dataentry of a value, ultrasonic or subsonic scanning techniques, manualdata entry, RFID-based scanning, scanning a 2D/3D barcode, using a wiredtechnology to scan, etc.

In some implementations, location beacon device 100 may be configured tobroadcast two different secured representations of the locationblockchain address at a time. For example, location beacon device 100may generate a first secured representation of the location blockchainaddress at a first time and a second secured representation of thelocation blockchain address at a second time after the first time, andtransmit a beacon including both secured representations of the locationblockchain address.

A user of user device 200 is configured to conduct an off-chaintransaction with agent system 300 and approve the off-chain transaction.For example, the user may be a customer or other party providing paymentor some other consideration in exchange for a good or service. In somecases, the off-chain transaction may be conducted using user device 200.Additionally, as further described below, user device 200 may beconfigured to communicate with agent system 300 to generate atransaction record on blockchain 800 including a reference to theoff-chain transaction, a secured representation of the blockchainaddress of the user, a secured representation of the blockchain addressof the agent, and other data.

User device 200 may be a mobile device such as a smartphone, tablet, ornotebook computer, a wearable device (e.g., smartwatch), a desktopcomputer, gaming console, smart speaker, or any other type of devicethat may be configured to approve a blockchain transaction including areference to an off-chain transaction made between the user of userdevice 200 and system 300. User device 200 may include a machinereadable medium 210, a processing device 220, a display 230, a receiver240, and transmitter 250.

Receiver 240 and transmitter 250 may be configured to receive ortransmit communications from/to agent system 300 and blockchain network700 during a process of creating and approving an off-chain transactionand/or a blockchain transaction including a reference to the off-chaintransaction. In implementations, receiver 240 and transmitter 250 maycomprise multiple receivers and/or transmitters. For example receiver240 and transmitter 250 may be implemented using Bluetooth®communication technology, NFC communication technology, cellularcommunication technology, Wi-Fi® communication technology, and/or somecombination thereof. It should be appreciated that although receiver 240and transmitter 250 are illustrated as being separate devices, in someimplementations they may be implemented as a transceiver.

Machine readable medium 210 of user device 200 may include a blockchainwallet 211, blockchain application 215, and off-chain wallet 218. Theblockchain wallet 211 may store the user's blockchain address 212, and apublic key 214 and private key 213 corresponding to the user'sblockchain address 212. For example, a public key 214 may be derivedfrom the private key 213, and the user's blockchain address 212 may bederived from the public key 214 by applying additional cryptographicalgorithm(s). In some implementations, public key 214 and blockchainaddress 212 are the same, in which case machine readable medium 210 maystore private key 213 and blockchain address 212. In someimplementations, blockchain wallet 211 may be a subcomponent ofblockchain application 215.

Blockchain application 215 may be provided by a party associated withagent system 300, off-chain verifier 400, or secured identify verifier500. For example, a retail store (agent) or a bank (verifier) mayprovide the blockchain application 315 through an online decentralizedapp store or other suitable medium. Alternatively, blockchainapplication 215 may be a native application of user device 200.

User device 200 may utilize blockchain application 215 to interact withagent system 300 and blockchain network 700 during a process of creatinga blockchain transaction record that includes a reference to anoff-chain transaction made between the user of user device 200 and agentsystem 300, secured representations of blockchain addresses of the userand agent, and/or a secured representation of a location blockchainaddress. To this end, blockchain application 215 may include approveblockchain transaction instructions 217 that may be executed by aprocessing device 200. Additionally, blockchain application 215 mayinclude time-based hash generation instructions 216, which may be asubcomponent of instructions 217.

Time-based hash generation instructions 216, when executed by processingdevice 220, apply a time-based cryptographic hashing algorithm to userblockchain address 212 to generate a secured representation of the userblockchain address. The secured representation of the user's blockchainaddress may be generated in substantially the same manner as describedabove with reference to location beacon device 100. For example, thesecured representation of the user's blockchain address may be generatedby applying a one-time cryptographic hashing algorithm using a currenttimestamp and the user's blockchain address. The current timestamp maybe obtained from processing device 220 (e.g., from a clock of theprocessing device). In some implementations, the user device 200 may usethe same time-based cryptographic hashing algorithm as a beacon device100. In other implementations, a different time-based cryptographichashing algorithm may be used. In some implementations, time-based hashgeneration instructions 216 may iterate to generate securedrepresentations of the blockchain address of user of user device 200,independent of whether a transaction occurs between the user device 200and agent system 300.

By virtue of user device 200 transmitting a secured representation ofthe user's blockchain address, which may be associated with anindividual such as a purchaser, personal information may be secured fromexposure and tampering from unauthorized entities. In particular, atransaction record may be created on a public or consortium blockchainthat hides the identity of the user from unauthorized parties. In someimplementations, for added security, an encrypted user blockchainaddress 212 is stored in machine readable medium 210 of the user device200. In such implementations, the encrypted user blockchain address 212is decrypted prior to applying the time-based cryptographic hashingfunction to produce the secured representation of the blockchainaddress.

The off-chain wallet 218 may include tokenized card data 219 that may bepresented by the user device 200 during an off-chain transaction withagent system 300. The tokenized card data may be associated with a bankcard issued by a banking authority or other entity, such as an authorityassociated with off-chain verifier 400. For example, the tokenized carddata may correspond to a credit card, debit card, charge card, loyaltycard, and/or other purchase related token that is used during anoff-chain transaction.

Agent system 300 may be configured to generate an off-chain transactionID from an off-chain transaction with a user, and write blockchaintransactions to the blockchain network 700, where the written blockchaintransactions may contain a reference to the off-chain transaction, andsecured representations of blockchain addresses of the user, agent,and/or transaction location. Agent system 300 may be implemented as anydistributed financial or value transaction system, including anautomated teller machine (ATM), POS system, card reader, cash register,etc. A POS system may include a POS terminal, mobile POS system (e.g.,mobile payment terminal), payment kiosk or any other POS system toprocess card payments. In implementations, the agent system may be asystem associated with a service or goods provider.

Agent system 300 may include a machine readable medium 310, a processingdevice 320, a display 330, a receiver 340, a transmitter 350, and a cardreader 360.

Receiver 340 and transmitter 350 may be configured to receive ortransmit communications from/to user device 200, blockchain network 700,and off-chain verifier 400 during a process of creating and approving anoff-chain transaction and/or a blockchain transaction including areference to the off-chain transaction. Receiver 340 may also receivebeacons broadcast by location beacon device 100. In implementations,receiver 340 and transmitter 350 may comprise multiple receivers and/ortransmitters. For example receiver 340 and transmitter 350 may beimplemented using Bluetooth® communication technology, NFC communicationtechnology, cellular communication technology, Wi-Fi® communicationtechnology, and/or some combination thereof. It should be appreciatedthat although receiver 340 and transmitter 350 are illustrated as beingseparate devices, in some implementations they may be implemented as atransceiver.

Machine readable medium 310 of agent system 300 may include an agentblockchain address 312, private key 313 and public key 314 correspondingto blockchain address 312, blockchain application 315, and instructions318 to create and verify off-chain transactions. Create and verifyoff-chain transaction instructions 318, when executed by a processingdevice 320, may generate an off-chain transaction ID and other off-chaintransaction information (e.g., timestamp, address, merchant ID, paymentamount, identifier of exchanged good or service, etc.) In someimplementations, create and verify off-chain transaction instructions318 may be implemented within blockchain application 315.

Blockchain application 315 may be provided by a party associated withagent system 300, off-chain verifier 400, secured identify verifier 500,or by a consortium of users 200. For example, a retail store (agent) ora bank (verifier) may provide the blockchain application 315.

Agent system 300 may utilize blockchain application 315 to writetransactions to blockchain network 700 that include: a reference to anoff-chain transaction ID associated with an off-chain transactionbetween a user of user device 200 and agent system 300, a securedrepresentation of the user blockchain address, a secured representationof the agent blockchain address, a secured representation of the agentlocation blockchain address, and/or other data. To this end, blockchainapplication 315 may include write blockchain transaction instructions317 that may be executed by a processing device 320. Additionally,blockchain application 315 may include time-based hash generationinstructions 316, which may be a subcomponent of instructions 317.

Time-based hash generation instructions 316, when executed by processingdevice 320, apply a time-based cryptographic hashing algorithm to userblockchain address 312 to generate a secured representation of the agentblockchain address. The secured representation of the agent's blockchainaddress may be generated in substantially the same manner as describedabove with reference to location beacon device 100 and user device 200.By virtue of system 300 transmitting a secured representation of theagent's blockchain address, information of provider such as a merchantmay be secured from exposure and tampering from unauthorized entities.In particular, a transaction record may be created on a public orconsortium blockchain that hides the identity of the agent fromunauthorized parties.

Card reader 360 may be configured to receive bank card data provided bya user of user device 200 (e.g., using a physical card or card datastored in a digital wallet). Card reader 360 may be implemented as achip card reader, a magnetic stripe reader, RFID card reader, NFC cardreader, or any other suitable card reader. In implementations thereceived card data may be encrypted, and/or card reader 360 may applyencryption for added security.

In some implementations, a location beacon device 100 may be integratedinto agent system 300 (e.g., in cases system 300 is fixed).

An off-chain verifier server system 400 (referred to herein as“off-chain verifier 400”) may be configured to conduct digitaltransactions off-chain. When there is an agent looking to confirmvalidity of a transaction, it may determine if a transaction associatedwith transaction ID shared by the agent has succeeded (e.g., sufficientfunds available for transaction and transaction approved by user), andit may also trigger a request to the secured identity verifier 500 toconfirm if a blockchain identity claimed by the user is valid. Forexample, to confirm the distributed identity of a user, the bank maycheck with a secured identity validator (e.g., central bank). Thisvalidation based on TOTAs of the user may provide a secondary validationof a transaction and prevent any spoofing or card theft or identitytheft based spurious transactions.

The off-chain verifier 400 may check i) if an off-chain transaction userand on-chain transaction user are the same; ii) if the location oforigination of a transaction and the registered location of the agent inits records are the same; iii) if the location of the transaction is notviolating any regulations or policies; and/or iv) if the user iseligible for any discounts or royalty points or other benefits based onthe location, agent, or purchase.

Off-chain verifier 400 may include a machine readable medium 410,processing device 420, and network interface 430. Machine readablemedium 410 may store instructions 411, that when executed by aprocessing device 420, query a secured identity verifier 500 to verify ablockchain transaction including secured representations of blockchainaddresses of two transacting parties (e.g., user and agent), and, insome implementations, a secured representation of a location blockchainaddress. Further, machine readable medium 410 may store instructions412, that when executed by a processing device 420, verify an off-chaintransaction. Additionally, machine readable medium 410 may storeinstructions 413, that when executed by a processing device 420, causeoff-chain verifier 400 to issue payment to an agent from funds afterattestation by secured identity verifier 500. This may provide forsecondary verification of a transaction and faster settlement.

Network interface 430 may be configured to communicate with agent system300, blockchain network 700, and/or secured identity verifier 500.

A secured identity verifier server system 500 (referred to herein as“secured identity verifier 500”) may be configured to verify blockchaintransactions and issue attestations to the blockchain network attestingto verified blockchain transactions. In particular, it may be configuredto receive queries from the off-chain verifier 400 to validate theidentity of the user, agent, and/or location of the transaction, and ifthey are valid. Secured identity verifier 500 may check the identitywith the blockchain address mapping server system and validate thetransaction on the blockchain. It may share the information with theoff-chain verifier 400 after verification. Based on the attestation fromthe secured identity verifier 500, a bank may run business logics suchas balance, location, agent, discounts and offers along with identitychecks to confirm the transaction and make settlements on-chain oroff-chain. In particular implementations, secured identity verifierserver system 500 may be implemented as a server system of a centralbank.

Secured identity verifier 500 may include a machine readable medium 510,processing device 520, and network interface 530. Machine readablemedium 510 may store instructions 514, that when executed by aprocessing device 520, verify a blockchain transaction including securedrepresentations of blockchain addresses of two transacting parties(e.g., user and agent), and, in some implementations, a securedrepresentation of a location blockchain address. Additionally, machinereadable medium 510 may store instructions 512, that when executed by aprocessing device 520, cause secured identity verifier 500 to sign(e.g., using private key 512) and write an attestation to the blockchainnetwork 700 that attests to the verified transaction.

Network interface 530 may be configured to communicate with off-chainverifier 400 and/or blockchain network 700. Network interface 530 mayalso be configured communicate with a blockchain address mapping serversystem 600, which as further described below, is configured to maintaina mapping between clear and secured representations of blockchainaddress (e.g., blockchain addresses associated with location beacondevices 100, user devices 200, and agent systems 300). Althoughblockchain address mapping server system 600 is illustrated in theexample of FIG. 1 as being separate from secured identity verifier 500,in some implementations blockchain address mapping server system 600 maybe integrated into verifier 500.

FIG. 7 is a sequence diagram illustrating a particular example methodthat may be implemented in the environment of FIG. 1 to createverifiable blockchain transaction record of a transaction between a userassociated with user device 200 and an agent associated with agentsystem 300, where the identities of the user and agent are hidden, inaccordance with implementations of the disclosure. The steps 901-917 ofthe sequence diagram will be referenced by way of example whendiscussing FIGS. 8, 9, 10, which illustrate example methods that mayrespectively be implemented by each of user device 200, agent 300, andoff-chain verifier 400/secured identity verifier 500.

FIG. 8 is an operational flow diagram illustrating an example method1000 that may be implemented by a user of user device 200, in accordancewith implementations of the disclosure. Some or all of the operations ofmethod 1000 may be implemented by a processing device 220 executingtime-based hash generation instructions 216 and approve blockchaintransaction instructions 217.

At operation 1010, the user performs a transaction with the agent toreceive an off-chain transaction ID. For example, as illustrated by step901 of FIG. 7, user device 200 may perform an off-chain transaction withagent system 300 that generates Tx-id. An off-chain transaction ID maybe a receipt number, an order number, bank transaction number, or anyother identifier of an off-chain transaction between the user and agentfor a good and/or service. The off-chain transaction ID may be generatedby the agent system 300 and provided to the user device 200.

In some implementations, the user provides bank card data during theoff-chain transaction. For example, a chip card reader, a magneticstripe reader, an RFID reader, an NFC device, or other suitablemechanism may be used by agent system 300 to obtain bank card dataassociated with a bank card issued to the user. In particularimplementations, user device 200 may provide tokenized card data 219during the off-chain transaction. For example, the user device 200 mayutilize NFC to communicate tokenized card data 219 to a card reader 360of agent system 300.

In some implementations, the user may be remotely located from theagent. For example, the user may be shopping for a product or serviceoffered by the agent over the internet, and the user may populate a formprovided over a web portal with bank card data. After submitting theorder including the populated web form, an off-chain transaction ID maybe generated.

At operation 1020, after the transaction ID is generated, the userdevice 200 provides a first secured representation of the user'sblockchain address to the agent system 300. For example, as illustratedby step 903 of FIG. 7, user device 200 provides RN1-U1 to agent system300 approving the transaction. The first secured representation of theblockchain address may be provided in response to receiving theoff-chain transaction ID from agent system 300, and it may signal anapproval of the transaction associated with the off-chain transactionID. A processing device 220 may execute time-based hash generationinstructions 216 to generate the first secured representation of theuser's blockchain address. In some implementation, the securedrepresentation of the blockchain address may already have been generated(e.g., the blockchain application may run in the background even when atransaction is not made).

At operation 1030, the user device 200 receives a request from the agentsystem 300 to verify a blockchain transaction including the off-chaintransaction ID and the first secured representation of the user'sblockchain address. In some implementations, the blockchain transactionmay also include a secured representation of the agent's blockchainaddress and/or a secured representation of a location blockchain addressof a location where the transaction took place. In implementations, therequest to verify the blockchain transaction includes a blockchaintransaction identifier (ID) of a transaction stored on blockchain 800 ofblockchain network 700. For example, as illustrated by step 905 of FIG.7, user device 200 may receive a request to verify a first blockchaintransaction Tx-B1, where the first blockchain transaction includes thefirst secured representation of the user blockchain address (RN1-U1), asecured representation of the blockchain address of agent system 300(RN1-U2), a secured representation of a location blockchain address(RN-L1), and the off-chain transaction ID (Tx-id).

At operation 1040, the user device 200 verifies the blockchaintransaction. In implementations, the user device 200 may look up theblockchain transaction associated with a blockchain transaction IDprovided by the agent system 300. The user device 200 may verify theblockchain transaction by confirming that the blockchain transactionincludes the off-chain transaction ID and the first securedrepresentation of the blockchain address of the user. For example, asillustrated by step 906 of FIG. 7, user device 200 may verify that firstblockchain transaction Tx-B1 includes Tx-id and RN1-U1. By virtue ofindependently verifying the blockchain transaction on the blockchain,the user device 200 may confirm that the secured representation of theuser blockchain address was associated with the correct off-chaintransaction.

At operation 1050, after verifying the blockchain transaction, the userdevice 200 provides a second secured representation of the userblockchain address to the server provider system 300. The second securedrepresentation of the user blockchain address may signal approval of theblockchain transaction. For example, as illustrated by step 907 of FIG.7, the user device 200 may provide RN2-U1, which signals approval ofTx-B1. The second secured representation of the user blockchain addressmay be generated by user device 200 at some time after the first securedrepresentation of the user blockchain address was generated (e.g., atime sufficient to change a one-time value generated by time-basedhashing). It may be generated in response to verifying the blockchaintransaction, or it may be a value that was already generated beforehand(e.g., by iteratively executing time-based hash generationinstructions).

In response to providing the second secured representation of the userblockchain address, and after further verification on the backend, userdevice 200 may receive a message from the agent system 300 of adistributed attestation transaction. The distributed attestationtransaction may attest to the truth of a second blockchain transactionincluding the second secured representation of the user blockchainaddress and a reference (e.g. blockchain transaction ID) to theblockchain transaction verified by the user device at operation 1040.For example, as illustrated by FIG. 7, at step 917, agent system 300 mayreceive distributed attestation transaction A-Tx-B2 that attests toTx-B2.

FIG. 9 is an operational flow diagram illustrating an example method1100 that may be implemented by agent system 300, in accordance withimplementations of the disclosure. Some or all of the operations ofmethod 1100 may be implemented by a processing device 320 executingtime-based hash generation instructions 316 and write and proveblockchain transaction instructions 317.

At operation 1110, agent system 300 generates an off-chain transactionID by conducting an off-chain transaction with a user. For example, auser may provide bank card data to initiate payment in exchange for agood or service. In the case of cash payment, for example, the off-chaintransaction ID may be generated by the billing system of a merchant.

After generating the off-chain transaction ID, agent system 300 maytransmit it to a user device 200 associated with the user. At operation1120, the agent system 300 receives a first secured representation ofthe user's blockchain address from user device 200. The received firstsecured representation of the blockchain address may indicate anapproval of the off-chain transaction, and may be provided by the userin response to a request from agent system 300. For example, asillustrated by FIG. 7, at step 902, agent system 300 requests RN1-U1.

At operation 1130, the agent system 300 generates a securedrepresentation of the agent's blockchain address. A processing device320 may execute time-based hash generation instructions 316 to generatethe secured representation of the agent's blockchain address.

At operation 1140, the agent system 300 transmits, to blockchain network700, a first blockchain transaction that comprises the off-chaintransaction ID, the first secured representation of the user'sblockchain address, and the secured representation of the agent'sblockchain addresses. In some implementations, the transmittedblockchain transaction may also include a secured representation of alocation blockchain address associated with a location. For example, asillustrated by FIG. 7, at step 904, agent system 300 writes a firstblock transaction Tx-B1 to blockchain 800 that contains RN1-U1, RN-U2,RN-L1, Tx-id. The agent system 300 may sign the first blockchaintransaction using its private key 313 prior to transmission of the firstblockchain transaction to the blockchain network 700.

Prior to operation 1140, agent system 300 may obtain the securedrepresentation of the location blockchain address from a beacontransmitted by a location beacon device 100. Alternatively, agent system300 may scan a fixed advertisement including the secured representationof the location blockchain address or obtain the secured representationof the location blockchain address in some other manner as discussedabove.

By virtue of writing a transaction to the blockchain network thatincludes secured representations of the user blockchain address, agentblockchain address, and, in some instances, a location blockchainaddress associated with a location where the transaction occurred, arecord of the parties involved in a transaction, as well as the place ofthe transaction, may be maintained on the blockchain that is viewable byany member of the consortium (or public, in the case of a publicblockchain), but only understandable by permissioned nodes (e.g.,secured identity verifier 500). Stated another way, the blockchaintransaction record protects the identities of the involved parties asnon-permissioned nodes will not be able to understand the random numbersgenerated by independent bodies or off-chain transaction ID that has nomeaning to non-parties to the off-chain transaction.

The blockchain transaction transmitted to the blockchain network 700 maybe validated by nodes on the blockchain network 700 using some suitableconsensus mechanism. By way of example, a signed blockchain transactionmay be broadcast by agent system 300 to all or a subset of nodes onblockchain network 700. Thereafter, the nodes of blockchain network 700may come to a consensus that validates the transaction and update theblockchain 800 with a block or a distributed ledger entry including thevalidated transaction.

At operation 1150, the agent system 300 queries the user device 200 toverify the first blockchain transaction. In implementations, the querymay include a blockchain transaction ID of the first blockchaintransaction that may be used by the user device 200 to look up theblockchain transaction after it has been validated by the blockchainnetwork 700.

At operation 1160, in response to the query, the agent system 300receives a second secured representation of the user's blockchainaddress. At operation 1170, the agent system 300 transmits, toblockchain network 700, a second blockchain transaction that comprises areference to the first blockchain transaction (e.g., the firstblockchain transaction ID) and the second secured representation of theuser blockchain address received from user device 200. For example, asillustrated by FIG. 7, at step 908, agent system 300 writes a secondblock transaction Tx-B2 to blockchain 800 that contains RN2-U1 andTx-B1. In implementations, device 300 may sign the second blockchaintransaction with its private key.

Thereafter, system 300 may share the first and second blockchaintransaction IDs (e.g., Tx-B1 and Tx-B2) with off-chain verifier 400, andrequest validation. For example, in the case of agent system 300belonging to a merchant, the merchant may request that the bank (e.g.,associated with off-chain verifier 400) clear the transaction and paythe merchant from the user's account. After validation, agent system 300may receive a reference to a distributed attestation verifying thesecond blockchain transaction. For example, as illustrated by FIG. 7, atstep 916, agent system 300 may receive distributed attestationtransaction A-Tx-B2 that attests to Tx-B2. The attestation of Tx-B2 mayprovide a chain of validation that attests that all of Tx-B2, Tx-B1 andTx-id are valid transactions between the parties (user and agent) at anapproved location, as Tx-B2 references Tx-B1 and Tx-B1 references Tx-id.

FIG. 10 is an operational flow diagram illustrating an example method1200 that may be implemented by off-chain verifier 400, in accordancewith implementations of the disclosure. Some or all of the operations ofmethod 1200 may be implemented by a processing device 420 executinginstructions 411-413.

At operation 1210, off-chain verifier 400 receives from agent 300 ablockchain transaction ID of first and second blockchain transactions,and a request to clear an off-chain transaction. For example, asillustrated by FIG. 7, at step 909, off-chain verifier 400 receivesTx-B1 and Tx-B2 along with a request to clear Tx-id. The secondblockchain transaction may include the blockchain transaction ID of thefirst blockchain transaction and a second secured representation of theblockchain address of the user. The first blockchain transaction mayinclude off-chain transaction ID, the first secured representation ofthe user blockchain address, and a secured representation of the agentblockchain address. In some instances it may also include a securedrepresentation of a blockchain address of the location of thetransaction.

At operation 1220, off-chain verifier 400 looks up the first and secondblockchain transactions. For example, as illustrated by FIG. 7, at step910, off-chain verifier 400 looks up blockchain transactions Tx-B1 andTx-B2 on blockchain 800.

At operation 1230, off-chain verifier 400 queries the secured identityverifier 500 to verify the first and second blockchain transactions. Forexample, the off-chain verifier 400 may send the first blockchaintransaction ID and second blockchain transaction ID to secured identityverifier 500 to perform the validation. For example, as illustrated byFIG. 7, at step 911, off-chain verifier 400 queries secured identityverifier to valid validate Tx-B1 and Tx-B2. Thereafter, off-chainverifier 400 may be notified by verifier 500 that the first and secondblockchain transactions have been verified.

Further, off-chain verifier 400 may verify the off-chain transaction.For example, in cases where off-chain verifier is associated with a bankof the user, it may determine that there are sufficient funds in theuser's account to provide to the agent (e.g., merchant). Verification ofthe off-chain transaction may occur before or after operation 1230. Insome cases, if the off-chain transaction is not verified (e.g.,insufficient funds), operations 1220-1240 may not be performed. Verifier400 may notify secured identity verifier 500 that the off-chaintransaction has been verified. In some implementations, the off-chainverifier 400 may request that the secured identity verifier 500determine if an off-chain ID of the user and first and second securedrepresentations of the user belong to the same entity.

In implementations, after verification by secured identity verifier 500,off-chain verifier 400 may receive from secured identity verifier 500 areference to a distributed attestation of the second blockchaintransaction that is stored on the blockchain 800 of blockchain network.For example, as illustrated by FIG. 7, at step 915, off-chain verifierreceives A-Tx-B2, which is an attestation of Tx-B2 recorded on theblockchain 800.

At operation 1240, off-chain verifier 400, may receive verification ofthe first and second blockchain transactions, and clear the off-chaintransaction. For example, it may issue payment to the agent 300. It mayalso send a reference of the distributed attestation to the agent.

In some cases, the off-chain verifier may perform some additional checksfor settlement such as comparing an approved location for the agent,discounts of the user, and loyalty points for the user. In these cases,in addition to the attestation, off-chain verifier 400 may look at otherparameters to complete a settlement or other transaction. In thesecases, the attestation address/identifier on the blockchain for an agentand a user transaction may be communicated by the off-chain validator tothe corresponding agent. In certain implementations, the off-chainverifier 400 may send the attestation reference to both user and agent.In some implementations, If timely updates are not sent by an agent oroff-chain verifier, a user may find the attestation by looking for asecured representation on the blockchain. The same may be done by theagent as well, removing any dependency on any single party of notcommunicating the attestation in a sequence, to allow for on-timeupdates.

FIG. 11 is an operational flow diagram illustrating an example method1300 that may be implemented by secured identity verifier 500, inaccordance with implementations of the disclosure. Some or all of theoperations of method 1300 may be implemented by a processing device 520executing instructions 514-515.

At operation 1310, secured identity verifier 500 receives a request fromoff-chain verifier 400 to verify first and second blockchaintransactions. In some implementations, the request may include an ID ofeach of the first and second blockchain transactions so that verifier500 may look them up on the blockchain. For example, as illustrated byFIG. 7, at step 912, secured identity verifier looks up Tx-B1 and Tx-B2for validation. The second blockchain transaction may include theblockchain transaction ID of the first blockchain transaction and asecond secured representation of the blockchain address of the user. Thefirst blockchain transaction may include the off-chain transaction ID,the first secured representation of the user blockchain address, and asecured representation of the agent blockchain address. In someinstances it may also include a secured representation of a blockchainaddress of the location of the transaction.

At operation 1320 verifier 500 verifies the first and second blockchaintransactions. In particular, central verifier server 500 may communicatewith a blockchain address mapping server system 600 including ablockchain address database 691 and time-based hash generationinstructions 692. The blockchain address database 691 may includingmappings between blockchain addresses and their secured representations.In particular database 691 may be configured to maintain, over time, amapping between user blockchain addresses and their respective securedrepresentations, agent blockchain addresses and their respective securedrepresentations, and/or location blockchain addresses and theirrespective secured representations. For example, database 691 may beused to map RN-L1 to the location blockchain address of device 100,RN1-U1 and RN2-U1 to the user blockchain address of device 200, andRN-U2 to the agent blockchain. In some implementations, separateblockchain address databases may be maintained for this purpose (e.g.,one database for locations, one database for users that are customers,and one database for agents that are merchants). To create this mapping,system 600 may use time-based hash generations instructions 692 togenerate the secured representation of the blockchain address. Theinstructions may apply the same time-based hashing algorithm that isapplied at each user device, location beacon device, or agent system 300to generate the same secured representation of the blockchain address.In some implementations, the mapping database may also provide mappingbetween off-chain account ids and on-chain blockchain addresses, iffinancial transactions are not carried out on-chain. This may helpprovide transitioning from traditional transactional systems todistributed value transactional systems.

As such, in response to a query received from off-chain verifier 400 toverify Tx-B1 & Tx-B2, central verifier server 500 may query systemblockchain address mapping server system 600 to retrieve clear versionsof the blockchain addresses and determines identities of the partiesinvolved in the transaction and the location of the transaction. Forexample, as illustrated by FIG. 7, at step 913, verifier 500 may accessserver to perform RN mapping to blockchain addresses and validation.Based on the business case, the systems may decide if additionalvalidation may be done at the secured identity validator or off-chainvalidator for checking additional conditions using a smart contract.This is optional and purely depends on the business case and howtransparent the entities are sharing business logics. In someimplementations both the secured identity verifier and off-chainverifiers may run additional smart contracts before signing attestationor doing further processing.

At operation 1330, secured verifier 500 digitally signs an attestation(e.g., using private key 512) attesting to the second blockchaintransaction (which also validates/provides attestation for Tx-B1 andTx-id as they are referenced in a chain) and transmits it to theblockchain network 700 to write to blockchain 800 to create adistributed attestation. For example, as illustrated by FIG. 7, at step914, the attestation A-Tx-B2 attesting to Tx-B2 is written on blockchain800. Thereafter, secured verifier 500 may communicate a blockchaintransaction ID of the distributed attestation to off-chain verifier 400(e.g. step 915).

In alternative implementations, verifier 400 may perform theverification of the first and second blockchain transactions itself(e.g., if customer and merchant use same bank). For example, it may haveaccess to blockchain address mapping server system 600. In yet otherimplementations, both verifiers 400 and 500 may have access toblockchain address mapping server system 600, and perform theverification of the first and second blockchain addresses. In suchimplementations, both verifiers 400 and 500 may come to a consensusbefore an attestation is generated.

Method and System for Using Non-Advertised Random Number Based HiddenIdentity for Verifiable Claims.

Referring again to the example of FIG. 7, after the user device 200verifies the first blockchain transaction corresponding to Tx-B1 on theblockchain 800, the user device 200 sends a second securedrepresentation of its blockchain address (e.g., RN2-U1) generated at asecond time to agent 300. Agent 300 is then configured to write a secondblockchain transaction Tx-B2 to the blockchain network 700, includingboth RN2-U1 and Tx-B1. However, if agent 300 were to associate RN1-U1with another blockchain transaction (e.g., not Tx-B1), user device 200may have no recourse to protest the invalid transaction involving userdevice 200 on the blockchain.

To this end, in some implementations, the second secured representationof the blockchain address associated with the user device may be maskedfrom agent 300. FIG. 12 illustrates one example sequence diagramillustrating a particular example method that may be implemented in theenvironment of FIG. 1 to mask the second secured representation of theuser blockchain address and create verifiable blockchain transactionrecord of a transaction between a user associated with user device 200and an agent associated with agent system 300, where the identities ofthe user and agent are hidden, in accordance with implementations of thedisclosure.

In particular, as contrasted with the sequence diagram of FIG. 7, whereuser device returns RN2-U1 to agent system 300 (step 907) afterverification of the first blockchain transaction, user device 200 mayinstead, at step 907-2, return a hash of Tx-B1 that uses RN2-U1 as ahashing key. In some implementations a timestamp (ts) is attached orotherwise included with the hash. This hash (and time stamp) may then beprovided to the agent system 300, which includes it along with Tx-B1 inthe second blockchain transaction that is written to the blockchain 800(labeled herein as step 908-2). In some implementations, this hashingfunction may be transparent to verifier provider system 400, in whichcase system 400 may not have knowledge that the value returned at step907-2 is a hash of Tx-B1 using RN2-U1, instead of RN2-U1 itself.

Secured identity verifier 500, which has access to blockchain addressmapping server system 600, may determine the hash H(Tx-B1, RN2-U1). Inparticular, at step 913-2, RN-C2 may be retrieved from database 691, andTx-B1 may be hashed using RN-C2 as a key. In implementations the correctkey RN-C2 may be first generated by using a timestamp attached to thehash to generate RN-C2. That hash may be compared with the hash writtenat Tx-B2 to validate the second blockchain transaction. By virtue ofthis implementation, a user device 200 may hide its identity to theagent system 300 (e.g., merchant) while still allowing for validation ofthe transaction. The foregoing implementation may provide advantagessuch as: hidden identity for claims than can be centrally verified;hidden identity in combination with blockchain to create verifiableclaims that are immutable; and hidden identity that can only by approvedentities having access to central systems with the ability to mapsecured representations of blockchain addresses.

FIG. 13 is an operational flow diagram illustrating an example method1400 that may be implemented by a user of user device 200, in accordancewith implementations of the disclosure. Some or all of the operations ofmethod 1000 may be implemented by a processing device 220 executinginstructions stored in a machine readable medium 210. In someimplementations, prior to implementing method 1400, operations 1010through 1040 may be performed as described above with reference to FIG.8.

At operation 1410, the user device 200 generates a second securedrepresentation of the user blockchain address. The second securedrepresentation of the user blockchain address may be generated afterverifying a blockchain transaction (e.g. operation 1040) looked up at anassociated blockchain transaction ID and including a first securedrepresentation of the user blockchain address and an off-chaintransaction identifier of an off-chain transaction involving the user.The second secured representation of the user blockchain address may begenerated by user device 200 at some time after the first securedrepresentation of the user blockchain address was generated (e.g., atime sufficient to change a one-time value generated by time-basedhashing). It may be generated in response to verifying a blockchaintransaction, or it may be a value that was already generated beforehand(e.g., by iteratively executing time-based hash generationinstructions).

At operation 1420, the user device hashes the blockchain transaction IDusing the generated second secured representation of the user blockchainaddress as a key.

At operation 1430, a timestamp is attached or otherwise associated withthe hash. The timestamp may be appended to the end of the hash. Thetimestamp may correspond to the time when the second securedrepresentation of the user blockchain address was generated (i.e., thetimestamp used to generate the second RN of the user).

At operation 1440, the hash and timestamp are provided to the agentsystem. The hash (and time stamp) may signal approval of the blockchaintransaction. For example, as illustrated by step 907-2 of FIG. 12, theuser device 200 may provide H(Tx-B1, RN2-U1), which signals approval ofTx-B1.

FIG. 14 is an operational flow diagram illustrating an example method1500 that may be implemented by a server system (e.g., verifier 500and/or blockchain address mapping server system 600), in accordance withimplementations of the disclosure. Some or all of the operations ofmethod 1000 may be implemented by a processing device executinginstructions stored in a machine readable medium.

At operation 1510, a request is received to verify first and secondblockchain transactions. In some implementations, the request mayinclude an ID of each of the first and second blockchain transactions,to allow the server system to look up the transactions on the blockchainnetwork 700. The first blockchain transaction may include the off-chaintransaction ID, a secured representation of the user blockchain address,and a secured representation of the agent blockchain address. It mayalso include a secured representation of a blockchain address of alocation of the off-chain transaction. The second blockchain transactionmay include the blockchain transaction ID of the first blockchaintransaction and a hash of the first blockchain transaction ID, with anappended time stamp. The secured representation of the user blockchainaddress included in the first blockchain transaction may have beengenerated at a time before the timestamp.

At operation 1520, a secured representation of the user blockchainaddress is generated using the timestamp. For example, a clear versionof the user blockchain address may be retrieved from database 691, and acryptographic time-based hash function may be applied to the userblockchain address and retrieved timestamp. For example, an HMACalgorithm may be applied. The timestamp may be retrieved from the secondblockchain transaction prior to operation 1520.

At operation 1530, a hash of the first blockchain transaction ID isgenerated using the generated secured representation of the userblockchain address as a key. At operation 1540, the generated hash iscompared with the hash included in the second blockchain transaction toverify that the hash included in the second blockchain transaction isvalid.

Method for Reusing Transaction Provenance & Distributed Attestation onBlockchain with Hidden Identity & Verifiable Claims

Following generation of a distributed attestation to a transaction on ablockchain (e.g. distributed attestation as described above withreference to FIGS. 1-14), the distributed attestation may serve as averifiable claim by a party involved in the transaction. For example, inthe environment of FIGS. 1-14, the distributed attestation, by virtue ofreferencing or including the off-chain transaction ID along with thesecured representation of the user's blockchain address, may serve as averifiable claim that the user can use as a proof of transacting anyvalue say buying goods, sharing data, spending time during thepurchaser's interaction with a particular service provider or agent(e.g., also included as a secured representation of the agent'sblockchain address). Further, by virtue of hiding the identities of theparties and/or the location as secured representations of blockchainaddresses, only approved parties may understand and/or act upon theattestation. A distributed attestation A-Tx-B2 may attest, for example,that transactions associated with IDs Tx-B2, Tx-B1, and Tx-id are validtransactions between claimed entities at an approved location for themto interact.

FIG. 15 illustrates an example environment by which a distributedattestation may be presented as a verifiable claim by an attestationholder associated with attestation holder device 1600 to a third partyverifier associated with third party verifier system 1700, in accordancewith implementations of the disclosure. In some cases, the attestationholder may correspond to a user of user device 200 that was involved ina transaction that is attested to on a blockchain network.

As illustrated in FIG. 15, and further described below, an attestationholder device 1600 is configured to obtain a distributed attestation,generate an encrypted message by encrypting (e.g., signing) thedistributed attestation with a private key of the attestation holder(e.g., private key 213) and public key of the third party verifier, andsending the encrypted distributed attestation to a third party verifiersystem 1700 as a verifiable claim. Encrypting the message with thepublic key of the recipient (third party verifier) ensures that it canbe only be unencrypted with the private key of the recipient, which isonly with the recipient. For simplicity of discussion, as used herein,the phrase “obtaining a distributed attestation” may refer to obtaininga copy of the distributed attestation stored on the blockchain orobtaining the identifier or address of the distributed attestation thatmay be used to lookup the distributed attestation on a blockchainnetwork. Similarly, the phrase “receiving a distributed attestation” (orencrypted messages including the distributed attestation) may refer toreceiving a copy of the distributed attestation stored on the blockchainor receiving an identifier or address of the distributed attestationthat may be used to lookup the distributed attestation on the blockchainnetwork.

In response to receiving the encrypted distributed attestation, thethird party verifier system 1700 may decrypt the encrypted message usingits private key and the public key (e.g., public key 214) associatedwith user 1600, determine that the message is a distributed attestation(e.g., by looking up the blockchain reference of the distributedattestation), and query secured identity verifier 1800 to determine ifthe distributed attestation is owned by or otherwise associated with theattestation holder. It may also send the distributed attestation tosecured identity verifier 1800 to determine if it is authorized toprovide a service or other response to the claim. The communicationbetween the third party verifier and the secured identity verifier maybe secured with public key infrastructure (PKI).

Secured identity verifier 1800 may determine based on an identity ofthird party verifier system 1700 (e.g., public key) if it is authorizedto access information relating to the distributed attestation. As such,the example environment of FIG. 15 allows for role-based control wherebya secured identity verifier can determine, based on the identity of arequesting third party verifier, whether the third party verifier ispermitted to validate and check identity of an attestation holder. Itshould be appreciated, however, that alternative systems withoutrole-based control of verifiers may be implemented. For example, in somecases an attestation holder may present the distributed attestation to aparty that was involved in a transaction attested to in the distributedattestation.

Secured identity verifier 1800 may access blockchain address mappingserver system 600 to map to clear versions any secured representationsof blockchain addresses appearing in the distributed attestation or intransactions referenced by the distributed attestation, and determine ifany of the blockchain addresses appearing in the distributed attestationor in a transaction referenced by the distributed attestation areassociated with the blockchain address (e.g., derived from the privatekey) of the attestation holder. If yes, secured identity verifier 1800may provide an indication to third party verifier system 1700 that theattestation holder is the owner or otherwise associated with thedistributed attestation, and thus has a claim. If no, secured identityverifier 1800 may provide an indication that the attestation holder isnot associated with the distributed attestation, and thus has no claim.In some implementations, an additional verifier may be involved in theprocess. For example, rather than query a secured identity verifier,third party verifier system 1700 may query another system that thenqueries the secured identity verifier 1800.

By way of illustrative example, consider an environment where adistributed attestation attests to a transaction involving a purchase ofa television. The distributed attestation may include a securedrepresentation of the purchaser's blockchain address. The purchaser,through a blockchain application, may encrypt a message including thedistributed attestation (e.g., reference or copy of attestation), andsend the encrypted message to a service center that repairs televisions(e.g., third party verifier) as part of a claims process. The servicecenter may present the distributed attestation to a secured identityverifier by sending it in a message encrypted with the service center'sprivate key and the public key of the secured Identity verifier. Thesecured identity verifier may confirm the identity of the purchaser andservice center. If the service center is approved based on its role toobtain information from the attestation, the secured identity verifiermay inform the service center that the attestation is a validattestation provided to the buyer.

FIG. 16 illustrates an example architecture of components of anattestation holder device 1600, in accordance with implementations ofthe disclosure. Device 1600 may comprise a machine readable medium 1610,processing device 220, display 230, receiver 240, and transmitter 250.The machine readable medium 1610 may comprise blockchain wallet 211 anda blockchain application 1615. Blockchain application 1615 may includeobtain distributed attestation instructions 1616, that when executed byprocessing device 220, obtain a distributed attestation stored on ablockchain network. Blockchain application 1615 may also include encryptdistributed attestation instructions 1617, that when executed byprocessing device 220, encrypt (e.g., using private key 213 and publickey of recipient) a message including the obtained distributedattestation. Blockchain application 1615 may further include submitencrypted distributed attestation as claim instructions 1618, that whenexecuted by processing device 220, transmit the encrypted message tothird party verifier system 1700. For example, the message may betransmitted as part of a claim made by the attestation holder device1600. In some implementations, an attestation holder device 1600 mayfunction as a user device 200.

FIG. 17 illustrates an example architecture of components of a thirdparty verifier system 1700, in accordance with implementations of thedisclosure. By way of illustrative example, third party verifier system1700 may correspond to a third party verifier such as a pharmacy storeascertaining the appropriate compliance in conditions needed to bemaintained by a supply chain company while transporting a medicine bychecking its attestation, a service center ascertaining the purchase andvalid warranty for a product for which a service is requested, anemployer ascertaining that its prospective employee had attended aseminar at a particular place and time as the employee claims, ane-retail company ascertaining that the drone of a drone delivery companyhad delivered a product to a customer at a point in space time formaking payments.

Third party verifier system 1700 may comprise a machine readable medium1710, a processing device 1720, and a receiver 1740 and transmitter 1750configured to receive or transmit communications from/to a device 1600or secured identity verifier 1800.

Machine readable medium 1710 may store a blockchain address 1712corresponding to the third party verifier, and a private key 1713 andpublic key 1714 corresponding to the blockchain address 1712. Machinereadable medium 1710 may also store a blockchain application 1715.Application 1715 may include instructions 1716, that when executed by aprocessing device 1720, receive, from a sender (e.g., attestation holderdevice 1600) an encrypted message including a distributed attestation,decrypt the message using a public key of the sender, and query asecured identity verifier 1800 to confirm that that the distributedattestation is associated with the sender.

FIG. 18 illustrates an example architecture of components of securedidentity verifier server system 1800, in accordance with implementationsof the disclosure. A secured identity verifier server system 1800(referred to herein as “secured identity verifier 1800”) may beconfigured to receive queries from a third party verifier system 1700 todetermine if a distributed attestation is owned by or otherwiseassociated with an attestation holder (e.g., by querying blockchainaddress mapping server system 600). It may also be configured todetermine if the third party verifier is authorized, based on itsidentity, to verify attestation identities (e.g., determine actualidentities of parties associated with secured represent of blockchainaddresses) contained in a distributed attestation. In particularimplementations, secured identity verifier may be configured todetermine if the third party verifier has role based access to obtainany information about a distributed attestation. Secured identityverifier 1800 may be implemented as a server system of a central bank.

Secured identity verifier 1800 may include a machine readable medium1810, processing device 1820, and network interface 1830. Networkinterface 1830 may be configured to communicate with attestation holderdevice 1600, third party verifier system 1700, and/or blockchain addressmapping server system 600.

Machine readable medium 1810 may store a blockchain address 1814corresponding to the third party verifier, and a private key 1815 andpublic key 1816 corresponding to the blockchain address 1814.

Machine readable medium 1810 may store instructions 1811, that whenexecuted by a processing device 1820, determine that a third partyverifier is authorized to verify identities of parties contained in adistributed attestation. Additionally, machine readable medium 1810 maystore instructions 1812, that when executed by a processing device 1820,cause secured identity verifier 1800 to determine identities of partiescontained in a distributed attestation (e.g., determine clear versionsof secured representations of blockchain addresses). Additionally,machine readable medium 1810 may store instructions 1813, that whenexecuted by a processing device 1820, cause secured identity verifier1800 to determine if a an attestation holder owns the distributedattestation (e.g., if a secured representation of the attestationholder's blockchain address appears in the distributed attestation).

FIG. 19 is an operational flow diagram illustrating an example method1900 that may be implemented by an attestation holder device 1600, inaccordance with implementations of the disclosure. Some or all of theoperations of method 1900 may be implemented by a processing device 220executing instructions 1616-1618.

At operation 1910, attestation holder device 1600 obtains a distributedattestation stored on a blockchain network. For example, the attestationholder device 1600 may obtain a blockchain ID of the distributedattestation or lookup the distributed attestation at its blockchain ID,and retrieve a copy. The distributed attestation obtained by theattestation holder device 1600 may comprise a secured representation ofthe blockchain address 212 of the user of the attestation holder device1600 or a reference to a blockchain transaction comprising the securedrepresentation of the user's blockchain address. The blockchain addressmay be associated with a private key of the user.

In particular implementations, the distributed attestation comprises anoff-chain transaction identifier or a reference to a blockchaintransaction comprising the off-chain transaction identifier. In someimplementations, the attestation holder device 1600 may maintain astored record of blockchain and/or off-chain transaction IDs that a userof the device was a party to, and use the stored record to lookupdistributed attestations.

At operation 1920, the attestation holder device 1600 generates anencrypted message by using a private key of the attestation holder and apublic key of a recipient (e.g., verifier such as a third party verifieror otherwise) to encrypt a message including the distributedattestation. Attestation holder device 1600 may use a private key 213derived from blockchain address 212 and the public key of the recipient(third party verifier) to generate the encrypted message.

At operation 1930, the attestation holder device 1600 transmits theencrypted message to a server (e.g. third party verifier system 1700) toverify a claim of the attestation holder. The attestation holder'spublic key may be known to all participants of the blockchain network.In this manner, it may be confirmed by the recipient (e.g., third partyverifier) that the attestation holder device 1600 is the originator ofthe message. Additionally, by using the public key of the recipient toencrypt the message only the recipient may decrypt the message using itsprivate key.

In various implementations, the attestation holder device 1600 maysubmit the distributed attestation to obtain consideration for a claim.For example, the user of the attestation holder device 1600 may presentthe distributed attestation for purposes of a warranty claim, aninsurance claim, a refund, to obtain a service, to receive payment forhaving provided a good, asset, and/or service, etc. The presenteddistributed attestation may be provided to prove a transaction done by auser in the past. In particular implementations, the distributedattestation provides proof of at least one of: the user's presence at alocation at a particular time; the user's custody of an asset orconsumption of a service, at a particular time; the user's purchase ofan asset or a service at a particular time; and the user's compliancewith handling of an asset or rendering of a service.

Following transmission of the encrypted message and verification by averifier, attestation holder device 1600 may receive a confirmationmessage confirming that the distributed attestation is a valid claimmade by the user. Thereafter the user of attestation holder may becompensated or receive a good, asset, or service for the claim. In someimplementations, the encrypted message is transmitted to a third partyverifier system 1700 that is configured to query a secured identityverifier to determine if a claimant of a distributed attestation is inthe fact the attestation holder. The secured identity verifier may,after determining that the third party verifier is authorized to obtaininformation about the distributed attestation (e.g., based on role basedaccess control), query a blockchain address mapping server system 600 toanswer the query. Alternatively, in other implementations, the encryptedmessage may be transmitted to a verifier system that access to ablockchain address mapping server system.

FIG. 20 is an operational flow diagram illustrating an example method2000 that may be implemented by a third party verifier system 1700(e.g., a server system), in accordance with implementations of thedisclosure. Some or all of the operations of method 2000 may beimplemented by a processing device 1820 executing instructions1811-1813.

At operation 2010 system 1700 receives a message encrypted with aclaimant's private key and the third party verifier's public key, theencrypted message including a distributed attestation stored on ablockchain network, where the distributed attestation includes a securedrepresentation of a blockchain address or a reference to the securedrepresentation of the blockchain address. The message may be submittedas part of a claim made by a claimant to an entity associated with thirdparty verifier system 1700.

In implementations, third party verifier system 1700 may determinewhether it can service or provide some type of action in response to theclaim made by the claimant. By way of particular example, afterdecrypting the message with the public key of the attestation holder andits own private key, the third party verifier system 1700 may reviewdistributed attestation A-Tx-B2 and observe that it contains anoff-chain transaction ID (e.g., Tx-id) that is valid. For example, theoff-chain transaction ID may be associated with purchasing a product,and the system 1700 may have database of valid off-chain transactionIDs, for which it may provide a warranty service, or other applicableservice.

At operation 2020, system 1700 uses a private key of an entityassociated with system 1700 (e.g., private key 1713) and a public key ofthe secured identity verifier (e.g., public key 1816) to encrypt amessage including the distributed attestation. In this manner, themessage may only be decrypted by the private key of the secured identityverifier. Additionally, the secured identity verifier can confirm thatthe third party verifier is the sender by using and successfullydecrypting the message using the public key of third party verifier.

At operation 2030, system 1700 transmits the second encrypted message tosecured identity verifier 1800 to determine if the claimant of thedistributed attestation is associated with the distributed attestation.attestation holder and/or to determine if the entity associated withsystem 1700 is authorized to view identities contained in thedistributed attestation.

Afterward, system 1700 may receive a message from the secured identityverifier 1800 confirming that the claimant is the distributedattestation holder. In response, a service may be performed for theclaimant. Alternatively, in cases where the distributed attestation doesnot include any secured representations of blockchain addressesassociated with the claimant, system 1700 may receive a message from theverifier 1800 indicating that the claimant is not the distributedattestation holder.

FIG. 21 is an operational flow diagram illustrating an example method2100 that may be implemented by a secured identity verifier 1800 (e.g.,a server system), in accordance with implementations of the disclosure.Some or all of the operations of method 2100 may be implemented by aprocessing device 1820 executing instructions 1716.

At operation 2110, verifier 1800 receives, from a server system, arequest from an entity (e.g., third party verifier) to determine if adistributed attestation stored on a blockchain is associated with anattestation holder. In various implementations, the request is encryptedusing a private key of the entity and a public key of the securedidentity verifier, and the distributed attestation includes a securedrepresentation of a blockchain address.

At operation 2120, verifier 1800 decrypts the message (e.g., using itsprivate key and public key of entity), and uses the public key of theentity to determine whether the entity (e.g., third party verifier) isauthorized to obtain information about the distributed attestation. Inparticular implementations, secured identity verifier may use the publickey of the entity to determine if the entity has role based accessrights to obtain any information (e.g., identities associated withsecured representations of blockchain addresses) about the distributedattestation. This determination may be made in accordance with a rolebased access control configured for a plurality of third partyverifiers, where the role based access control may be used to validatedif a third party verifier has rights to access information from adistributed attestation.

If the entity is authorized to obtain information from the distributedattestation transaction, at operation 2130 verifier 1800 may transmit aresponse message to the entity indicating if the claimant of thedistributed attestation is associated with (e.g., the holder of) thedistributed attestation. In implementations, the response message maynot share any information about the distributed attestation other thanconfirming that the claimant of the distributed attestation is (or isnot) the attestation holder.

To this end, prior to transmitting the response message, verifier 1800may determine if the claimant of the distributed attestation isassociated with the distributed attestation by querying a database(e.g., database 691) that maintains, over time, a mapping betweensecured representations of blockchain addresses and their clearversions. During the query, verifier 1800 may determine clear versionsof blockchain addresses in the distributed attestation, and determine ifthe one of the clear versions of the blockchain address is associatedwith the claimant (e.g., based on the public key of the claimant).

The illustrated systems and methods for using a distributed attestationas a verifiable claim by a party involved in a transaction may provideseveral benefits. They may provide an environment where identity in theverifiable claims is hidden and based on location, using a centralizedsystem (e.g., secured identity verifier 1800) to control verification ofattestation. They may provide a role-based control system for verifierswho can validate and check identities of holders of verifiable claims.Additionally, holders of verifiable claims may share information orattestation using public/private keys to service providers and a securedidentity verifier, which showcases the consent from the holder forsharing information with a service provider in the distributedecosystem.

FIGS. 22-24 illustrate three particular examples of distributedattestations that may be presented by a user to a verifier during averifiable claims process. FIG. 22 illustrates a distributed attestation2200 that may be presented by a user (e.g., attestation holder) as partof a claims process where the user is required to show that they werepresent at a particular location at a particular time. For example,distributed attestation 2200 may be presented by an individual to provetheir attendance at a seminar or workshop held in a particular locationin the past, for which the individual is now seeking credit.

Distributed attestation 2200 may be recorded on a blockchain of anysuitable blockchain network, or it may be recorded on some otherblockchain of a blockchain network. Distributed attestation 2200 mayinclude a blockchain transaction ID 2201, a secured representation of auser's blockchain address 2202, a secured representation of an agentblockchain address 2207, the agent being a service provider or otheragent with whom the transaction was made by the user, a securedrepresentation of a location blockchain address 2203, a timestamp 2204identifying when the attested event occurred (e.g., when user was at thelocation), a digital signature 2205 of a verifier (e.g., securedidentity verifier) attesting to the data contained in the attestation,and other transaction data 2206 (e.g., public keys associated withlocation, user, and verifier that signed attestation, and atransactional timestamp showing when the attestation was actuallygranted by the verifier).

FIG. 23 illustrates a distributed attestation 2300 that may be presentedby a user to a verifier as part of a claims process where the user isrequired to show that the user had custody of an asset at a particularlocation and time. For example, distributed attestation 2300 may bepresented to a third party verifier to prove that user delivered apackage at a particular time in the past.

Distributed attestation 2300 may be recorded on a blockchain of anysuitable blockchain network. Distributed attestation 2300 may include ablockchain transaction ID 2301, a secured representation of the user'sblockchain address 2302, a secured representation of the assetblockchain address 2303, a secured representation of the locationblockchain address 2304, a secured representation of an agent blockchainaddress 2308, the agent being a service provider or other agent withwhom the transaction was made by the user, a timestamp 2305 identifyingwhen the event occurred (e.g., when user had custody of the asset), adigital signature 2306 of a verifier attesting to the data contained inthe attestation, and other transaction data 2307 (e.g., public keysassociated with location, asset, user, and verifier that signedattestation, transactional time stamp showing when the attestation wasactually granted by the verifier).

FIG. 24 illustrates a distributed attestation 2400 that may be presentedby a user to a verifier as part of a claims process where the user isrequired to demonstrate the veracity of a captured image along with theidentity of an entity embedded in the captured image. For example,distributed attestation 2400 may include an image or reference to animage of two vehicles after a collision, along with a securedrepresentation of a blockchain address of an owner of one of thevehicles. In this scenario, the distributed attestation may be presentedby the owner of the vehicle for an insurance claim to prove an accidentoccurred at a particular time and place between two vehicles.

Distributed attestation 2400 may be recorded on a blockchain of anysuitable blockchain network. Distributed attestation 2400 may include ablockchain transaction ID 2401, a secured representation of an entityblockchain address 2402 (e.g. vehicle of owner presenting claim), areference to an image 2403, a timestamp 2404 of the time when the imagewas taken by the user, a digital signature 2405 of a verifier (e.g.,secured identity verifier) attesting to the data contained in theattestation, and other transaction data 2406 (e.g., securedrepresentation of location blockchain address, secured representation ofuser blockchain address, GPS coordinates, and/or public keys associatedwith entity, verifier that signed attestation, location, a timestamp ofthe transaction, and/or user, etc.). In implementations, the referenceto the image 2403 may be a pointer, which may be the blockchain addressof a storage location or storage transaction that stores the image onthe blockchain network. In other implementations, the distributedattestation may include the image.

As illustrated by the foregoing example distributed attestations2200-2400, although they are available for viewing by other nodes on ablockchain network, they disclose a limited amount of information. Inparticular, they include secured representations of blockchain addressescorresponding to users (e.g., carrier of client device), locations,assets, and/or entities. By virtue of disclosing a limited amount ofinformation, the identities of users, locations, assets, and/or entitiesassociated with a transaction may be masked from other nodes on ablockchain network that do not need to know this information. Further, auser or other attestation holder associated with the securedrepresentation of the a blockchain address in the distributedattestation may provide the distributed attestation as a verifiableclaim to any authorized verifier as needed.

In this document, the terms “machine readable medium,” “computerreadable medium,” and similar terms are used to generally refer tonon-transitory mediums, volatile or non-volatile, that store data and/orinstructions that cause a machine to operate in a specific fashion.Common forms of machine readable media include, for example, a harddisk, solid state drive, magnetic tape, or any other magnetic datastorage medium, an optical disc or any other optical data storagemedium, any physical medium with patterns of holes, a RAM, a PROM,EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, andnetworked versions of the same.

These and other various forms of computer readable media may be involvedin carrying one or more sequences of one or more instructions to aprocessing device for execution. Such instructions embodied on themedium, are generally referred to as “instructions” or “code.”Instructions may be grouped in the form of computer programs or othergroupings. When executed, such instructions may enable a processingdevice to perform features or functions of the present application asdiscussed herein.

In this document, a “processing device” may be implemented as a singleprocessor that performs processing operations or a combination ofspecialized and/or general-purpose processors that perform processingoperations. A processing device may include a CPU, GPU, APU, DSP, FPGA,ASIC, SOC, and/or other processing circuitry.

In this document, a “server system” may refer to a system of one or moreservers.

As described herein, user devices, agent systems, server systems,verifiers, beacon devices, and other devices may implement some or allof their components within a trusted execution environment.

The various embodiments set forth herein are described in terms ofexemplary block diagrams, flow charts and other illustrations. As willbecome apparent to one of ordinary skill in the art after reading thisdocument, the illustrated embodiments and their various alternatives canbe implemented without confinement to the illustrated examples. Forexample, block diagrams and their accompanying description should not beconstrued as mandating a particular architecture or configuration.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code components executed by one or more computer systems or computerprocessors comprising computer hardware. The one or more computersystems or computer processors may also operate to support performanceof the relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). The processes and algorithms may beimplemented partially or wholly in application-specific circuitry. Thevarious features and processes described above may be used independentlyof one another, or may be combined in various ways. Differentcombinations and sub-combinations are intended to fall within the scopeof this disclosure, and certain method or process blocks may be omittedin some implementations. Additionally, unless the context dictatesotherwise, the methods and processes described herein are also notlimited to any particular sequence, and the blocks or states relatingthereto can be performed in other sequences that are appropriate, or maybe performed in parallel, or in some other manner. Blocks or states maybe added to or removed from the disclosed example embodiments. Theperformance of certain of the operations or processes may be distributedamong computer systems or computers processors, not only residing withina single machine, but deployed across a number of machines.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, the description of resources, operations, orstructures in the singular shall not be read to exclude the plural.Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps.

Terms and phrases used in this document, and variations thereof, unlessotherwise expressly stated, should be construed as open ended as opposedto limiting. Adjectives such as “conventional,” “traditional,” “normal,”“standard,” “known,” and terms of similar meaning should not beconstrued as limiting the item described to a given time period or to anitem available as of a given time, but instead should be read toencompass conventional, traditional, normal, or standard technologiesthat may be available or known now or at any time in the future. Thepresence of broadening words and phrases such as “one or more,” “atleast,” “but not limited to” or other like phrases in some instancesshall not be read to mean that the narrower case is intended or requiredin instances where such broadening phrases may be absent.

What is claimed is:
 1. A non-transitory computer readable mediumcomprising instructions that when executed cause a device comprising aprocessor to: receive, at the device from a system, an off-chaintransaction identifier (ID) associated with an off-chain transactioninvolving a user; in response to receiving the off-chain transaction IDfrom the system, provide, from the device to the system, a first securedrepresentation of a distributed ledger address associated with the user,wherein the first secured representation is generated by applying atime-based cryptographic hashing algorithm using a first currenttimestamp and the distributed ledger address associated with the user;receive, at the device from the system, a request to verify adistributed ledger transaction, the distributed ledger transactioncomprising the off-chain transaction ID and the first securedrepresentation of the distributed ledger address; in response to therequest, verify, at the device, the distributed ledger transaction byconfirming that the distributed ledger transaction includes theoff-chain transaction ID and the first secured representation of thedistributed ledger address; and after verifying the distributed ledgertransaction, provide, from the device to the system, a second securedrepresentation of the distributed ledger address associated with theuser, wherein the second secured representation is generated by applyingthe time-based cryptographic hashing algorithm using a second currenttimestamp and the distributed ledger address associated with the user.2. The non-transitory computer readable medium of claim 1, whereinreceiving the request comprises receiving a distributed ledgertransaction ID associated with the distributed ledger transaction. 3.The non-transitory computer readable medium of claim 2, whereinverifying the distributed ledger transaction comprises looking up adistributed ledger to find the distributed ledger transaction associatedwith the distributed ledger transaction ID.
 4. The non-transitorycomputer readable medium of claim 1, wherein the system is to write thedistributed ledger transaction to a distributed ledger network, thedistributed ledger transaction written by the system to the distributedledger network comprising the off-chain transaction ID.
 5. Thenon-transitory computer readable medium of claim 1, wherein theinstructions when executed cause the device to: generate the firstsecured representation of the distributed ledger address at a first timeusing the first current timestamp associated with the first time; andgenerate the second secured representation of the distributed ledgeraddress at a second time, after the first time, using the second currenttimestamp associated with the second time.
 6. The non-transitorycomputer readable medium of claim 1, wherein the distributed ledgertransaction further comprises a secured representation of a distributedledger address associated with the system or an owner of the system. 7.The non-transitory computer readable medium of claim 1, wherein thedistributed ledger transaction further comprises: a securedrepresentation of a distributed ledger address associated with alocation of the off-chain transaction; and a digital signature of thesystem.
 8. The non-transitory computer readable medium of claim 1,wherein the providing of the first secured representation of thedistributed ledger address from the device to the system signals anapproval of the off-chain transaction by the device.
 9. Thenon-transitory computer readable medium of claim 1, wherein theproviding of the second secured representation of the distributed ledgeraddress from the device to the system signals an approval of thedistributed ledger transaction by the device.
 10. A method comprising:performing, by a device with a system, an off-chain transactioninvolving a user; receiving, at the device from the system, an off-chaintransaction identifier (ID) associated with the off-chain transaction;in response to receiving the off-chain transaction ID from the system,providing, from the device to a distributed ledger application of thesystem, a first secured representation of a distributed ledger addressassociated with the user, wherein the first secured representation isgenerated by applying a time-based cryptographic hashing algorithm usinga first current timestamp and the distributed ledger address associatedwith the user; receiving, at the device, a request from the distributedledger application to verify a distributed ledger transaction, thedistributed ledger transaction comprising the off-chain transaction IDand the first secured representation of the distributed ledger address;in response to the request, verifying, by the device, the distributedledger transaction by confirming that the distributed ledger transactionincludes the off-chain transaction ID and the first securedrepresentation of the distributed ledger address; and after verifyingthe distributed ledger transaction, providing, from the device to thedistributed ledger application, a second secured representation of thedistributed ledger address associated with the user, wherein the secondsecured representation is generated by applying the time-basedcryptographic hashing algorithm using a second current timestamp and thedistributed ledger address associated with the user.
 11. The method ofclaim 10, wherein receiving the request comprises receiving adistributed ledger transaction ID associated with the distributed ledgertransaction, and wherein verifying the distributed ledger transactioncomprises looking up a distributed ledger to find the distributed ledgertransaction associated with the distributed ledger transaction ID. 12.The method of claim 10, wherein the distributed ledger transactionfurther comprises: a secured representation of a distributed ledgeraddress associated with the system; and a secured representation of adistributed ledger address associated with a location of the off-chaintransaction.
 13. A system comprising: a processor; and a non-transitorycomputer readable medium storing instructions executable on theprocessor to: generate an off-chain transaction identifier (ID)associated with an off-chain transaction involving a user; send theoff-chain transaction ID from the system to a device; receive, at thesystem from the device, a first secured representation of a distributedledger address associated with the user, wherein the first securedrepresentation is generated by applying a time-based cryptographichashing algorithm using a first current timestamp and the distributedledger address associated with the user; generate a securedrepresentation of a distributed ledger address associated with thesystem; and transmit a first distributed ledger transaction to adistributed ledger network, the first distributed ledger transactioncomprising the off-chain transaction ID, the first securedrepresentation of the distributed ledger address associated with theuser, and the secured representation of the distributed ledger addressassociated with the system.
 14. The system of claim 13, wherein theinstructions are executable on the processor, to obtain a securedrepresentation of a distributed ledger address associated with alocation where the off-chain transaction occurred, wherein the firstdistributed ledger transaction transmitted to the distributed ledgernetwork further comprises the secured representation of the distributedledger address associated with the location.
 15. The system of claim 13,wherein the instructions are executable on the processor: query thedevice to verify the first distributed ledger transaction; receive, atthe system from the device in response to the querying, a second securedrepresentation of the distributed ledger address associated with theuser, wherein the second secured representation is generated by applyingthe time-based cryptographic hashing algorithm using a second currenttimestamp and the distributed ledger address associated with the user;and transmit a second distributed ledger transaction to the distributedledger network, the second distributed ledger transaction comprising anidentifier of the first distributed ledger transaction and the secondsecured representation of the distributed ledger address associated withthe user.
 16. The system of claim 15, wherein querying the device toverify the first distributed ledger transaction comprises transmitting adistributed ledger transaction ID associated with the first distributedledger transaction to the device.
 17. The system of claim 15, whereinthe instructions are executable on the processor to receive adistributed attestation identifier of a distributed attestationattesting to the second distributed ledger transaction.
 18. The systemof claim 17, wherein the instructions are executable on the processor totransmit the distributed attestation identifier to the device.
 19. Thesystem of claim 13, wherein the receiving of the first securedrepresentation of the distributed ledger address associated with theuser at the system from the device signals an approval of the off-chaintransaction by the device.
 20. The system of claim 13, wherein theinstructions are executable on the processor to sign the firstdistributed ledger transaction with a private key of the system prior totransmitting the first distributed ledger transaction to the distributedledger network.